home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
pcboard
/
cbfree13.zip
/
WHATSNEW.!!!
< prev
Wrap
Text File
|
1996-06-08
|
9KB
|
240 lines
───────────────────────────────────────────────────────────────────────────
6/2/96
1. User record phone number matches CID, but CB-Free still making
a callback (when sysop has configured to upgrade immediately).
Problem: Callbacks being done even when phone numbers match when
the SysOp has it configured to upgrade immediately.
Solution: Change variable types as we were overloading the variable
Reported by: John Palazzolo
2. Improve Log reporting - Improve logging information.
3. All callbacks are Long Distance
Problem: All callbacks are now treated as Long Distance when the
DISALBED code is used for Long Distance callback times
allowed.
Soltion: Fix the code :)
Reported by Charles Shapiro and "The Doctor", and Gary Sterr
4. Updated AREACODE.DAT file. Thanks to Charles Shapiro and his
Co-SysOp, "The Doctor", for the update.
*** CBFREE13.ZIP Released to the Public ***
───────────────────────────────────────────────────────────────────────────
5/1/96
1. Help new users enter their entire phone number in the proper format.
Problem: Some users when prompted for their phone number only enter
their exhange+last 4, omitting the area code.
Solution: Write a small, quick, FREE, with source PPE to check the
users phone numbers in their user record. This PPE should
be called from the security display files for a new user.
If the phone numbers are not in the proper format, PHONE.PPE
will prompt them to correct it. Once correct, CB-FREE will
be able to use these phone numbers for callback.
2. Another companion program added to CB-FREE
A. CB-STATS.ZIP - A companion program for CB-FREE which generates
an output report containing statistics gathered
from CB-FREE Node?.Log files. The output file
can be in color (PCB Color Codes) or in ASCII.
Examples of the output files are included in
this archive with the names CB-STATS.EX1 and
CB-STATS.EX2
**** CBFREE12.ZIP released to the Public *****
───────────────────────────────────────────────────────────────────────────
4/17/96
1. Display more info to the user
Problem: SysOp wants to display a file when the CID number matches
the user record phone number. This file would inform the
user they will automatically be upgraded, after name and
number checking.
Solution: Add a file to be displayed: "CIDNFO" if: 1. The file
exists in the SAME DIRECTORY as the PPE, 2. The CID phone
number matches the user record phone number, 3. The SysOp
has configured CD-FREE to automatically upgrade the user
when the user record phone number matches the CID number.
*** This is an OPTIONAL file - It is NOT REQUIRED ***
Reported by: John Palazzolo
───────────────────────────────────────────────────────────────────────────
4/11/96
1. More information in the log files to review CID information and User
record phone number entries.
Problem: Not enough logging information for troubleshooting.
Solution: Add logging of RAW (PPE has not parsed, nor modified)
CID and User Record Phone number information.
───────────────────────────────────────────────────────────────────────────
4/3/96
1. OS/2 system reporting problems with callback program after user
is not contacted successfully for one reason or another.
Problem: After PPE exits and returns to PCB, CPU usage is at 30%
and window is "frozen" until SysOp closes and reopens
it.
Solution: Alter code to turn "ON" Carrier Detect checking and
keyboard timeout checking right before exiting the PPE.
As I do not run OS/2, this fix is being sent to reporting
SysOp for testing, and not other SysOps at this time.
Reported by: Darrell Harder
───────────────────────────────────────────────────────────────────────────
3/28/96
1. User getting disconnected when CID matches user record and
call is LD.
Problem: When a user is calling LD and CID matches the user record
the user is being disconnected after NO CALLBACK is made
(configured not to callback if CID matches user record
phone numbers - User is then automatically upgraded).
Solution: Fix the code <G>. Set the variable local_call to TRUE
so during the EXIT_PROG subroutine, the user is not
disconnected. The log will properly show the number
is long distance and the log will also show the users
phone numbers matches the CID info. local_call = TRUE
is to keep the program from haning up on the user.
Reported by: John Palazzolo
2. SysOp wants to stop any user who is blocking CID info from performing
a callback. This appears as PRIVATE or BLOCKED for the NMBR and
NAME fields in the CID info (other strings maybe used instead of
PRIVATE or BLOCKED - check with your local Phone Co.)
Problem: SysOp does not want a user who is blocking CID info from
using the callback PPE.
Solution: Add two parameters to the configuration file for CID
support. The old .CFG entry would look like:
TRUE;TRUE;NMBR =;301;A
The new .CFG entry will look like:
TRUE;TRUE;NMBR =;301;A;TRUE;PRIVATE
^^^^^^^^^^^^
Two New Parameters
TRUE = Stop all users who BLOCK CID information
FALSE = Allow user to continue (default)
PRIVATE = string to search for to determine if user
is trying to block their CID info. Another
string used is BLOCKED. Check with your
local phone company for the string to
search for in your area.
NOTE: Some local phone companies allow you to stop any calls where
a user is blocking caller id. This is stopped at the central
office and never reaches your BBS. The user will receive a
recording informing them of the inability to call the desired
number with CID blocked. Again, check with your local phone
company for this option.
This feature was added for SysOps whose their local phone
company does not provide CID blocking prevention.
Reported by: Marvin Blackburn
───────────────────────────────────────────────────────────────────────────
3/2/96
1. Caller ID not being detected/used by PPE
Problem: CID Phone number not being picked up by PPE
Solution: Only the phone number was being passed to
PCB, so the Caller ID string did not have
any strings to search for (like "NMBR =").
If in the configuration file, the string
to search for is NOTHING (TRUE;TRUE;;301;A)
the PPE will look for the phone number
starting at the beginning of the CID
string.
Examples: 3014445555
3014445555 NAME: JOE USERNAME
Reported by: John Palazzolo
───────────────────────────────────────────────────────────────────────────
2/29/96
1. Need ability to block ALL Long Distance Callbacks
Problem: No real way to block ALL long distance callbacks
Solution: If the phrase "DISABLED" appears in the long distance
times allowed entry in the configuration file, no
long distance phone calls will be allowed. The
file LDNO will be displayed.
Reported by: Pete Stan
───────────────────────────────────────────────────────────────────────────
2/16/96
1. Need for a SUFFIX number when dialing LD.
Problem: No suffix added when dialing LD.
Solution: Add a suffix to the configuration file and make it
definable by sysop as to when the suffix is used.
Reported by: Nick Chandley
───────────────────────────────────────────────────────────────────────────
2/14/96
1. Murphy has struck again!!! A problem with Caller ID surfaced
right after release...typical!! This new version fixes the
problem with Caller ID.
Problem: Log would show "=" as the phone number, and the user
would get an error that "=" is not an acceptable
area code (if you had area code checking turned on).
The log would state the Caller ID number does not
match an entry in the users record.
Solution: Fix the code!!! Caller ID was broken when the Hex
ASCII feature was added.
Reported By: Bob Lotspeich
**** CBFREE11.ZIP released to fix this problem *****